Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Expose CROSSPLANE_NAMESPACE to uptest #1108

Merged

Conversation

mbbush
Copy link
Collaborator

@mbbush mbbush commented Jan 24, 2024

Description of your changes

Since we started consuming upbound/official-providers-ci#169, running make uptest or make e2e locally fails on the import step unless the CROSSPLANE_NAMESPACE env var is defined. This sets it in the uptest makefile step.

It would be great to backport this to at least 0.47, just to make local development on that branch easier, but I don't think I have permission to add the appropriate label.

I have:

  • Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

Running uptest locally now passes without any additional env vars set.

Copy link
Collaborator

@ytsarev ytsarev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the catch, I hit the same in other Crossplane Configurations today and end up with the identical fix, so fully sure it's working.

@ytsarev
Copy link
Collaborator

ytsarev commented Jan 24, 2024

/test-examples="examples/docdb/cluster.yaml"

just in case, to have a centralized uptest run

@jeanduplessis jeanduplessis merged commit 702122c into crossplane-contrib:main Jan 24, 2024
10 checks passed
mbbush added a commit to spanio/upbound-provider-aws that referenced this pull request Feb 15, 2024
ulucinar pushed a commit to ulucinar/upbound-provider-aws that referenced this pull request Feb 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants